Method and apparatus for data analytics management

ABSTRACT

An improved system and method for providing data analytics management (DAM), in particular for wireless networks having multiple domains, is disclosed. Some embodiments utilize a hierarchical DAM structure. Such a hierarchy includes a Global DAM function which provides inter network DAM, and domain DAM functions which provide intra network DAM. Some embodiments utilize a plurality of local DAM functions within a domain. In some embodiments, the global DAM can be implemented by a third party. In other embodiments, different networks inter operate by utilizing virtual network slices over non-owned infrastructure to provide what appears to be a global network by each operator. For such embodiments, DAM can be performed on a per slice basis.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of priority to U.S. patentapplication Ser. No. 62/219,497, entitled “METHOD AND APPARATUS FOR DATAANALYTICS MANAGEMENT” filed Sep. 16, 2015, which is hereby incorporatedby reference in its entirety.

FIELD OF THE INVENTION

The present invention pertains to the field of data analyticsmanagement.

BACKGROUND

Wireless networks include a number of infrastructure elements. Suchinfrastructure elements include access points or base stations, forcommunicating with mobile devices, gateways, functional service nodesthat offer services such as Authentication Authorization and Accountingas well as Policy and Charging Rule enforcement functions. A mobiledevice should be understood as a device that connects to a mobilenetwork, and includes user equipment (UE) and other wireless devices.These different geographical transmission regions may be managed andoperated by different wireless network service providers, each of whichutilize a variety of infrastructure elements for providing communicationservices to devices.

Mobile Devices can include devices which communicate using the wirelessinfrastructure, but are not typically mobile. An example of such devicesincludes smart meters, which provide utility companies with usageinformation using machine type communication (MTC). There may bethousands of such MTC devices, all using the same service.

There is a need to collect and analyze data relating to thecommunication services provided to wireless devices. Conventionally thiscollecting and analyzing of data has involved the infrastructureelements logging (collecting) data and transmitting the logged data torequesters. However, the increasing number of devices being deployed andthe increasing number or infrastructure elements to provide service tothis increasing number of devices, coupled with the fact that networksmay be operated and used by different entities, present challenges forcollecting and analyzing this data. For example, with the increasingnumber of devices using wireless networks, significant network resourcesmay be used for logging and reporting data potentially with overlappingdata being transmitted to various parties. This can use up networkresources which could be better used to provide network services tocustomers.

This background information is provided to reveal information believedby the applicant to be of possible relevance to the present invention.No admission is necessarily intended, nor should be construed, that anyof the preceding information constitutes prior art against the presentinvention.

SUMMARY

Accordingly an object of embodiments of the present invention is toprovide an improved system and method for providing data analyticsmanagement (DAM). Rather than having every infrastructure element logdata and potentially transmit large amounts of data, at multiple timesto different parties, embodiments provide a centralized service forcollecting and providing data to satisfy different requests fromdifferent parties. Embodiments may be of particular use for wirelessnetworks, and in particular for wireless networks having multipledomains. Some embodiments utilize a hierarchical DAM architecture. Sucha hierarchy includes a Global DAM entity which provides inter networkDAM, and domain DAM entities which provides intra network DAM. Someembodiments utilize a plurality of local DAM entities within a domain.In some embodiments, the global DAM can be implemented by a third party.In other embodiments, different networks inter operate by utilizingvirtual network slices over non-owned infrastructure to provide whatappears to be a global network by each operator. For such embodiments,DAM can be performed on a per slice basis.

In some embodiments, DAM entities are instantiated and/or configured ondemand. In some embodiments, a local DAM entity can beinstantiated/configured either by, or in response to instructions from,a domain DAM.

In some embodiments, there is provided a distributed DAM topology with adomain DAM entity consolidating data received from a plurality of localDAM entities, and providing results to requesters, which may come from aglobal DAM function. This can be used for data logging, network resourceutilization, charging and other applications. Further, in someembodiments DAM entities can provide on-demand services to other networkoperation services and network customers, including virtual networkoperators, over-the-top (OTT) network customers (who typically operatetheir own networks for providing content to users) and enterprisecustomers.

Other aspects provide for processing systems which include a processorand machine readable memory storing software instructions which, whenexecuted, cause said processor to carry out the methods disclosedherein, including instantiating and migrating the virtual entities whichimplement said methods.

An aspect of the present invention provides a method of providing dataanalytics information, the method executed by a first data analyticsmanagement (DAM) function. Such a method includes receiving a requestfor data analytics information from a requester. Such a method furtherincludes configuring a plurality of DAM network functions to collectnetwork data. Such a method further includes receiving the network datafrom the plurality of DAM network functions. Such a method furtherincludes consolidating the network data to produce the requested dataanalytics information to satisfy the request. Such a method furtherincludes supplying the requested data analytics information to therequester. In some embodiments configuring a plurality of DAM networkfunctions comprises instantiating any DAM network functions which havenot been previously instantiated and are needed to satisfy the request.In some embodiments receiving the network data includes retrieving thenetwork data from a database populated by each of the plurality of DAMnetwork functions. In some embodiments the first DAM function is anetwork domain function and each of the plurality of DAM networkfunctions are local DAM functions instantiated to collect data fromlocal network infrastructure elements. In some embodiments the local DAMfunctions are instantiated close to the local network infrastructureelements. In some embodiments the local DAM functions are instantiatedwithin a node for collecting data from a cluster of networkinfrastructure elements. In some embodiments the location of the localDAM functions are dependent on the nature of the request. In someembodiments the local DAM functions supply different types of data, withthe data being supplied being dependent on the request. In someembodiments the first DAM function is a global domain function andconfiguring a plurality of DAM network functions comprises configuring aplurality of domain network functions for providing DAM information onper domain basis, with each domain function configured to configurelocal DAM functions for collecting local DAM data from local networkinfrastructure elements. In some embodiments the requester is aninfrastructure manager function. In some embodiments the requester is aCustomer Service Management (CSM) function. In some embodiments therequester is a third party. In some embodiments the requester is networkcustomer who is supplied a virtual network slice by a wireless networkoperator who operates the data analytics management (DAM) function andthe request includes a request for network slice utilization. In someembodiments the request for data analytics information includes arequest for network slice utilization for a particular network slice,and wherein configuring a plurality of DAM network functions to collectnetwork data comprises configuring a plurality of DAM network functionsto collect network data regarding usage from infrastructure elementsutilized by the particular network slice.

Another aspect of the present invention provides a data analyticsmanagement (DAM) network function. Such a DAM function includes anetwork interface for receiving a data analytics request and fortransmitting instructions. Such a DAM function further includes aprocessor and a non-transient memory for storing instructions which whenexecuted by the processor cause the data analytics management networkfunction to carry out the methods as described herein. In someembodiments the instructions cause the DAM function to configure aplurality of additional DAM network functions to collect network datadependent on a request for data analytics information received from arequester. Such instruction further cause the DAM function network toconsolidate data received from the plurality of additional DAM networkfunctions to produce the requested data analytics information to satisfythe request. Such instructions further cause the DAM function to supplythe requested data analytics information to the requester. In someembodiments the instructions to configure a plurality of additional DAMnetwork functions comprise instructions to instantiate any additionalDAM network functions which have not been previously instantiated andare needed to satisfy the request. In some embodiments the DAM functionis a network domain function and each of the plurality of additional DAMnetwork functions are local DAM functions instantiated to collect datafrom local network infrastructure elements. In some embodiments thelocal DAM functions are instantiated close to the local networkinfrastructure elements. In some embodiments the local DAM functionssupply different types of data, with the types of data being suppliedbeing dependent on the request. In some embodiments DAM network functionof claim 15 wherein the DAM function is a global domain function and theinstructions to configure a plurality of additional DAM networkfunctions comprises instructions to configure a plurality of domainnetwork functions for providing DAM information on per domain basis,with each domain function configured to configure local DAM functionsfor collecting local DAM data from local network infrastructureelements. In some embodiments the request for data analytics informationincludes a request for network slice utilization for a particularnetwork slice, and wherein the instructions to configure a plurality ofadditional DAM network functions to collect network data comprisesinstructions to configure a plurality of local DAM network functions tocollect network data regarding usage from infrastructure elementsutilized by the particular network slice.

BRIEF DESCRIPTION OF THE FIGURES

Further features and advantages of the present invention will becomeapparent from the following detailed description, taken in combinationwith the appended drawings, in which:

FIG. 1 schematically illustrates a series of base stations logging andsupplying data to a plurality of requesters.

FIG. 2 illustrates an embodiment of a data analytics management (DAM)system which interacts with requesters and infrastructure.

FIG. 3 illustrates a wireless communications network (WCN) architecturewhich includes DAM functions, according to an embodiment.

FIG. 4 is a flowchart illustrating a method of providing data analyticsinformation according to an embodiment

FIG. 5 is a flowchart illustrating DAM interaction with aninfrastructure manager, according to an embodiment.

FIG. 6 is a flowchart illustrating DAM interaction with a CustomerService Management (CSM) entity according to an embodiment.

FIG. 7 is a flowchart illustrating DAM interaction with a CSM entityaccording to another embodiment.

FIG. 8 is a flowchart illustrating DAM interaction with a VirtualNetwork Operator (VNO) according to another embodiment.

FIG. 9 illustrates a processing system that may be used for deploymentor instantiating components of the WCN.

DETAILED DESCRIPTION

Next generation of wireless communications network (WCN) architecturesare envisioned to provide a plurality of services to a plurality oftypes of customers using such features as Network FunctionVirtualization (NFV) and network slicing. Further there may differenttypes of entities involved with providing communication services,including Virtual Network Operators (VNOs) who provide virtual networkservices, possibly using network infrastructure which is not owned orcontrolled by the VNOs.

With the advent of the internet of things (IoT), many thousands ofdevices can connect to a wireless network. Such devices are calledmachine type communication (MTC) devices which includes smart meters,which provide utility companies with usage information). Further,network operators may provide virtual networks to each utility, forexample with each utility provided a network slice. Each utility mayrequest data regarding its network usage, for example for network sliceutilization, or for management functions such as monitoring the servicebeing received, for forecasting or for scheduling communications duringoff-peak periods if dynamic (surge) pricing is used.

FIG. 1 schematically illustrates a series of base stations logging andsupplying data to a plurality of requesters. In this example threeaccess points (APs) 10, 20, 30, which may be base stations or othertypes of access nodes are shown. In this example two utilities, namely agas utility 40 and an electric utility 50 are shown, as is a networkoperator 60. Each AP can provide connectivity to a large number ofdevices. For example AP 10 can provide connectivity to a large number ofgas utility meters 70 and electric utility meters 80. Similarly, AP 20can provide connectivity to a large number of gas utility meters 71 andelectric utility meters 81 and AP 30 can provide connectivity to a largenumber of gas utility meters 72 and electric utility meters 82. Each APcan provide connectivity to other devices (not shown). Each AP 10, 20,30 logs data regarding network usage. This data can be requested byvarious requesters. For example for gas utility 40 to obtain networkutilization data for its devices, it would need to request data,possibly via an operation subsystem (OSS) from each AP by sendingrequest 41 to AP 10, request 42 to AP 20 and request 43 to AP 30. Thegas utility may do this for quality of service (QoS) or quality ofExperience (QoE) assurance purposes, in order to obtain service deliveryperformance statistics and distributions. Similarly electric utility 50may request data from each AP, again possibly via an OSS, by sendingrequest 51 to AP 10, request 52 to AP 20 and request 53 to AP 30.Similarly network operator 60 would need to request data from each AP bysending request 61 to AP 10, request 62 to AP 20 and request 63 to AP30. As can be appreciated, this is just an example and a typical networkwould have many additional APs, and requesters. Consequently theserequests, and the subsequent responses, utilize network resources whichcan be significant, especially as the number of devices, and types ofdata to be logged increases.

Accordingly, rather than have each AP log data and provide the raw datato a number of different requesters, embodiments provide data analyticsmanagement (DAM) systems and methods which can collect and provide data,and in some embodiments analyze the data to satisfy different requestsfrom different parties.

FIG. 2 schematically illustrates interaction between DAM functions andother components according to an embodiment. In this embodiment, a DAMsystem 200, controlled by a wireless network operator, collects andanalyzes data received from General Wireless Network Infrastructure(GWNI) elements 230. GWNI elements 230 include Radio Access Network(RAN) nodes such as receivers, antennas, base stations (BS), basetransceiver stations (BTS), Node-B, evolved Node-B (eNodeB), a homeNode-B, a home eNodeB, site controllers, APs, data centers, C-RANclusters which include Remote Radio Heads (RRHs) controlled by asuitable controller, and other network components including networkelements and links which route data between these nodes and othernetworks. The infrastructure elements 230 relay raw network data to theDAM system 200. The DAM system 200 can collect, consolidate, and in somecases analyze the data to provide information to the different entitiesaccording to the nature of each request. Accordingly, in someembodiments the DAM system 200 can provide a centralized aggregator ofthe different types of data to satisfy requests, and can provide and/oranalyze different types of data depending on the nature of the request.As such, in some embodiments the DAM system can be configurable and canprovide DAM as a service by providing on demand DAM to requesters. Insome embodiments the DAM system 200, which can appear as a singlecentralized function, can actually be a distributed system. Accordingly,as will be explained below, the DAM system 200 can comprise a pluralityof DAM entities. Accordingly, the DAM entities receive a request forinformation from a requester. The DAM entities receive the raw data fromthe GWNI elements, analyze this logged information and then outputresults to the requester. The results may be in the form of a databasewhich is compiled by the DAM entities. As discussed above, the DAMentities may be organized into a hierarchical architecture. This enablesthe DAM entities to offer “DAM as a service” to DAM customers, in whichthe hierarchy of DAM entities acts as an interface to the GWNI forproviding various types of data relating to network operations torequesters.

The requesters can include Infrastructure Management (InfM) entities240, Customer Service Management (CSM) entities 250, or networkcustomers 260. The infrastructure elements 230 will be owned by aservice provider, but it should be appreciated that they are notnecessarily owned by the same wireless network operator (WNO) as theowner of the DAM entities which receive the data. For example, a virtualnetwork (VN) operator (VNO) may provide a VN service which operates overa WNO's infrastructure, for example by means of network slice. In thiscase, the VNO may operate DAM entities which collect and analyzeinformation received from the WNO's infrastructure. Alternatively, theVNO may be the requester, and receive information from the WNO's DAMentities. One example of the information which can be provided by theDAM is slice resource utilization. This can be useful in determiningwhether the slice paid for is appropriate, or whether a larger orsmaller slice should be utilized. In addition to indicating whether alarger or smaller slice should be utilized, some embodiments can alsoprovide an indication of the amount of resources which should be eitheradded to or reduced from the current slice. Further, some embodimentscan inform whether any additional resources (for a larger slice) areavailable.

An InfM entity 240 is responsible for management of the GWNI 230, or asubset of the GWNI 230. It should be appreciated that not all of theGWNI elements 230 will necessarily be owned and operated by the sameentity, and there may be a plurality of InfM entities. For example, anInfM entity 240 can be responsible for one or more of node configurationin the wireless access network, integration of private networks,integration of private Data center, and network topology configuration.The InfM entity 230 can request network statistics logs via a managementplane interface, such as through an existing M-M interface as defined bythe 3^(rd) Generation Partnership Project (3GPP), for example through anM-M application program interface (API). The InfM entity 240 manages theinfrastructure elements to allocate resources as needed to providerequested services. For example, the InfM 240 can turn off nodes whenthey are not needed and can throttle services or borrow resources whenneeded and available (possibly from other networks) when capacity doesnot meet demand. To do this the InfM entity 240 would requestinfrastructure resource utilization statistics and distribution. Forexample the InfM entity 240 would request traffic load distributionacross a geographical area (which can include the load in clouds (e.g.,within a data center) and in links).

The CSM entity 250 can also make requests via an MM API. It should beappreciated that CSM is a broad category, and can provide a variety offunctions. For example, CSM can include quality of experience (QoE)assurance management, to ensure that quality of service (QoS)/QoErequirements are satisfied. For example, a CSM module 250 can track,analyze and report on such factors as QoS and delay. The CSM module 250can track patterns and can allocate/change resources if need be toensure QoE requirements are met. For example the CSM module 250 can be aCSM-QoS assurance function, which can request service deliveryperformance statistics and distributions, possibly on a per slice basis.As another example the CSM module 250 can be a CSM-QoS managementfunction which can request e.g., per slice load statistics anddistributions and/or per slice resource utilization and distributions.Accordingly the CSM module 250 requests network data, which can beprovided by DAM entities 200 described herein. CSM 250 can also includecontext management function in which different contexts may be definedfor different services, and different contexts may be managed on aservice-by-service basis. For example the CSM module 250 can be aCSM-Context function which can request, for example, device commutepattern statistics and/or device communication pattern statistics.Another example is CSM charging. It should be appreciated that intypical LTE networks, logging traffic and charging is performed by aPacket Gateway (P-GW). However this only works for traffic flows betweenthe wireless network and the internet. As more functions are providedinside the RAN, there is likely to be larger volumes of traffic that donot leave the network. In addition to being able to charge for theprocessing of data in the RAN, an operator may need the ability tocharge customers for inter-network traffic. Furthermore, even whencharging is not a factor, being able to obtain traffic statistics fortraffic that does leave the network is important for network sliceprovisioning in networks that make use of virtualization. Accordingly,there is a need for CSM charging and logging for more general dataflows. Embodiments provide a distributed logging and charging CSMsolution. Each of these will be discussed in more detail below. Anotherexample includes CSM Authentication and Authorization. More details of aCSM application which can interface with the DAM entities of the presentdisclosure are discussed in U.S. provisional patent Ser. No. 62/169,084filed Jun. 1, 2015, which is hereby incorporated by reference in itsentirety.

Accordingly the DAM system 200 provides data analytics management (DAM)which provides data log and analytics service to all above entitiesbased on the requirements of the requesting entity. In some embodimentsthe DAM system 200 is the only management entity which is provided dataaccess from the GWNI. This way other management entities are isolatedfrom the raw data to avoid the unnecessary duplication of requests (andthe resulting drain on resources). In some embodiments the DAM system200 enables “data analytics as a service” which can be provided to botha network operator's management entities and also to 3rd parties. Insome embodiments, this is simplified by the use of unified interfacessuch as M-M APIs.

Referring to FIG. 3, there is shown an embodiment of a wirelesscommunications network (WCN) which includes a hierarchical dataanalytics management (DAM) logical architecture. This architectureincludes a logical topology with various DAM functions deployed ondifferent components of the WCN. The WCN includes two network operatordomains (Domain A 360 and Domain B 380), linked by a high capacitytransport network 300. Each domain has a domain DAM function associatedwith it. The example DAM hierarchy illustrated in FIG. 1 includes aglobal DAM function 310, which can be deployed in a Data Center (DC)Cloud, and in some embodiments may be administered by a third partytrusted by each domain operator. Below the global DAM is a plurality ofdomain DAM function (D-DAM) 320, 322. Each domain DAM function can bedeployed in conjunction with a Service Oriented Network Auto Creation(SONAC) instance 361, 381, if needed. Each domain can have a pluralityof local DAM functions (L-DAMs). Domain A 360 is shown to include L-DAM332 associated with an access point 333, which could be a cluster ofremote radio heads, centrally controlled by one or more controllers.Domain A 360 also includes L-DAM 330 associated router 331. Domain B 380is shown to include L-DAM 382 associated with an access point 383, andL-DAM 392 associated with an access point 393. It should be noted thatthis is a simplified drawing, with only two infrastructure elementsshown per domain, but there would typically be many infrastructureelements in a domain. Further a local DAM can be associated with aplurality of APs (i.e., relays and in some embodiments analyzes datagenerated by a plurality of APs). As will be discussed below, there arepotentially multiple levels of DAM functions (e.g.,global/domain/local/etc.). However such a distributed system can includemore levels for larger networks. For example, a local DAM can beresponsible for collecting data for a local region of a few squarekilometers, whereas a city DAM can collect and analyze data from thelocal DAMs within a city, and there may be regional DAMs in the nextlevel of the hierarchy, with a provincial or national DAM above that.Example embodiments will be discussed with reference to a simplifiedhierarchy including local, domain and global levels, each with their ownDAM entities.

In the implementation of a large network, it may be advantageous todivide the network into a series of smaller network segments. In someimplementations, different network segments may be created on sets ofinfrastructure operated by different infrastructure providers. Thesesegments may form the basis for different network domains and can beconsidered a separate network with a network ID. The global DAM 310collects and analyzes data on an inter-domain basis. It can provideon-demand data analytics information for any network segment overseen bya D-DAM, and global data analytics information based on the dataaccessible to the global DAM. In some embodiments, DAM services can beprovided on-demand at any level in the hierarchy. It should beappreciated that in some embodiments, the global DAM entity may not beneeded for a network operator with a single domain which does notrequire inter-domain DAM.

As used herein, “SONAC” refers to a Service Oriented Network AutoCreation technology, which can be thought of as a software controller.In various embodiments, SONAC includes three enabling technologies,namely Software Defined Topology (SDT), Software Defined ResourceAllocation (SDRA), and Software Defined Protocol (SDP). In a given SONACinstance, some or all of SDT, SDRA and SDP may be used. Which of thesetechnologies are included in a given SONAC instance can be controllable.In embodiments where the network makes use of virtualization, some ofthese SONAC functions may reside in an orchestrator.

As shown in FIG. 3, embodiments can include a hierarchical logicaltopology of the DAM entities, each providing different aspects of DAM. Aglobal DAM 310 can manage the DAM requirements of a network, or acrossnetworks, through interactions with domain specific DAM entities 320 and322. The global DAM function 310 is communicatively coupled to domainDAM entities 320, 322 through a transport network 300. Domain DAM 320may receive and reply to requests from a requester 325 and global DAM310 may receive and reply to requests from a requester 315, as will bediscussed below. Within a domain, a plurality of local DAM functions isestablished, as shown by way of example through the plurality ofinstances from 330, 332, 382 and 392. Domain specific DAM functions andthe Global DAM functions may be virtualized entities supported by a datacenter, or across a number of data centers. These entities can be eitherdiscrete entities or virtualized functions resident in a cloudenvironment. Similarly, the local DAM functions can be supported by adata center, or may be instantiated as software modules executing onprocessors of local network infrastructure elements.

Local DAM functions may be instantiated as needed to perform edge DAMfunctions. In some embodiments, this can be done on a per-user orper-device basis. In other functions, there is another level of virtualuser DAM functions reporting to the Local DAM. It should be appreciatedthat each DAM function may be geographically separated and individuallydeployed on different components of a WCM (not shown). Although notshown, a service specific virtual DAM entity could also be instantiatedto serve the needs of MTC devices that all interact with the sameservice.

Local DAM (L-DAM) functions will now be discussed, according toembodiments. A local DAM entity can log, analyze and report oninfrastructure parameters within a local area, for example a couple ofsquare kilometers. However it should be appreciated that the size of alocal DAM area will depend on the population density, expected traffic(both amount and types), and the types of GWNI in the area, as well asthe processing power and bandwidth that can be dedicated to the localDAM functions. In some embodiments, the local DAM will simply relay datato another function (for example the domain DAM), which will analyze thedata. In other embodiments, the local DAM can analyze (or partiallyanalyze the data), and provide the analysis to the domain DAM, with orwithout data. Local DAM functions can be established for individualinfrastructure elements, of for clusters of infrastructure elements.Accordingly, decisions of where to physically place, or instantiate,local DAM functions can use strategies similar to those used in decidingwhere to place network infrastructure nodes. Further, for networks whichuse Network Function Virtualization (NFV), DAM functions can beinstantiated along with other Virtualized Network Functions (VNFs), suchas a virtual service-specific or user-specific Serving Gateway(v-s/u-SGW). In some embodiments, such user or service specific DAMfunctions can be local DAM functions. In other embodiments, service/userspecific DAM functions can be instantiated when needed, in ahierarchical level below the local DAMs.

Examples of local DAM functionality will now be discussed, according toembodiments. A local DAM function can provide a raw data log on demand(e.g., upon request). Such a data log can include network resourcestatus, traffic load status and service delivery status. The networkresource status can include physical network resource statusinformation, including link status and processor status. It should beappreciated that the processor status may be derived from thebuffer/queue status. The physical network resource status can beprovided by the WNO infrastructure elements for the WNO usage. This canbe provided to the InfM in response to a request from the InfM. Virtualnetwork/slice resource status data can also be provided—for exampleslice resource utilization statistics, which can be provided by the VNO.Examples of the service delivery statistics include slice service QoEstatistics (which may be requested by a WNO CSM-QoE entity, or by theVNO), or per customer or service QoE statistics (which may be requestedby a WNO CSM-QoE entity or by customers of the WNO).

These status reports can be provided to the domain DAM (which canaggregate and provide more comprehensive reports to the requester) ordirectly to the requester (e.g., CSM or InfM entities). The reports neednot be transmitted directly from the local DAM to the domain DAM. As analternative, the local DAM functions may save data to one or moredatabases, which may be accessed by the domain DAM functions. As well asraw data, a local DAM entity can provide local data analyticsinformation upon request.

In some embodiments, the local DAM functions are instantiated andconfigured by the domain DAM function, possibly by sending a request toa software defined topology (SDT) entity, such as an orchestrator.

Domain DAM (D-DAM) functions will now be discussed, according toembodiments. The D-DAM functions instantiate and configure the L-DAMfunctions. As should be appreciated, the D-DAM functions can determinethe location for the L-DAM functions (for example, in relation to thenetwork topology). Alternatively other network functions may provideinput on where such functions should be placed. A SONAC instance orVirtual Network Function Manager (and/or Orchestrator) may carry out theinstantiation and configuration of VNF L-DAM entities, based oninstructions from the D-DAM functions. The D-DAM functions collectinformation from the L-DAMs and analyze the data. The DAM data includesnetwork resource management related data, which may be of interest tothe WNO or to WNO's customers, for example VNO operators. The WNO maycollect and analyze domain wireless network resource utilization andtraffic load distribution over a geographic area or on a domain or slicebasis, for example for GWNI resource pool management purposes.Similarly, a VNO may collect and analyze slice resource utilization andtraffic load distribution over a geographic area or on a domain or slicebasis, in order to ascertain the need for VN/Slice updates. For example,a VNO can monitor slice utilization to determine if a larger or smallerslice is needed to meet current demand levels. The D-DAM data can alsoinclude QoE assurance data useful for charging and/or renegotiation forthe levels of service provided. This QoE data can depend on the type ofcustomer. For example QoE includes latency and rate for individualcustomers, or whether a satisfactory ratio was delivered for domain VNOcustomers. Vertical customers, for example, utility companies or otherenterprise network operators, typically have multiple devices using acombination of services. The QoE/QoS data for such customers includesstatistics of rate, latency etc., which can be analyzed over all or asubset of their devices.

The D-DAM data can be made available to either the global DAM or otherrequesters by saving the data to one or more accessible databases.

Global DAM functions will now be discussed, according to embodiments. Insome situations, a WNO may subdivide a network into different domainsfor management reasons. The global DAM function can be administered by aWNO to provide information across its entire network. Alternatively, theglobal DAM function can be operated by a 3^(rd) party which providesinter-network information to and about each WNO, in which case each WNOcan be considered a domain. The global DAM functions are similar tothose of the D-DAM functions, but provide a global view of the loaddistribution over a geographic area. This can be useful to WNOs whoprovide or utilize VNs using the GWNI of other WNOs. As but one example,a global DAM can be useful for supplying data analytics information tocustomers who may have network services provided by more than one WNO.For example a utility company may have some meters served by a firstWNO, while other meters, possibly in another city, served by a secondWNO. The global DAM can consolidate network usage for the entire utilitycompany, by interacting with a domain DAM associated with each WNOnetwork.

A method of providing data analytics information according to anembodiment is illustrated in FIG. 4. Such a method can be executed by afirst data analytics management (DAM) function. The method includes atstep 410 receiving a request for data analytics information from arequester. The method further includes at step 415 configuring aplurality of DAM network functions to collect network data. The methodfurther includes at step 420 receiving the network data from theplurality of DAM network functions. The method further includes at step430 consolidating the network data to produce the requested dataanalytics information to satisfy the request. The method furtherincludes at step 440 supplying the requested data analytics informationto the requester. Additional non-limiting examples which provide moredetails to supplement these method steps depending on such factors asthe nature of the request, and network configuration, will now bediscussed.

A procedure for DAM interaction with an InfM requester will now bediscussed with reference to FIGS. 3 and 5, according to an embodiment.FIG. 5 is a flowchart illustrating DAM interaction with a domain InfMentity according to an embodiment. In this example, the requester 325 isa domain InfM module. The domain InfM sends a request 510 to the D-DAM320, for example for network resource statistics and/or traffic loadstatistics. It should be appreciated that this example also works for aglobal InfM acting as requester 315 of the global DAM 310. In responseto the request, the D-DAM 320 configures 520 the L-DAMs 330, 332. Itshould be appreciated that this step assumes the L-DAMs are alreadyinstantiated but if not, the L-DAMs would be instantiated first. It isnoted that in this specification DAMs may be used as short form for DAMentities or functions. The L-DAMs reply 530 with the results, which canbe via signaling to the D-DAM. The reply may be in the form oftransmitted data, or a notification of a database creation/update withthe requested data which can be accessed by the D-DAM. The D-DAM 320then replies 540 to the requester 325 (in this example, the InfM).

A procedure for DAM interaction with a CSM requester will now bediscussed with reference to FIGS. 3 and 6, according to an embodiment.FIG. 6 is a flowchart illustrating DAM interaction with a global CSMentity according to an embodiment. In this example, the requester 315 isa Global CSM entity, for example a CSM-QoE function providing QoEassurance on a per customer basis. The CSM function sends request 610for QoE statistics to the Global DAM function 310. The QoE statisticscan be requested on a per service basis, per customer basis or otherbasis. Global DAM 310 forwards the request 620 to domain DAMs 320, 322.The domain DAMs 320, 322 configure 620 the local DAMs. In particular,domain DAM 320 configures L-DAMs 330, 332, whereas domain DAM 322configures L-DAMs 382, 392. It should be appreciated that the local DAMsshould be instantiated prior to configuration. Accordingly, if any ofthe local DAMs are not already instantiated, the domain DAM functionwill cause them to be instantiated in NFV enabled nodes (e.g., networkelements). In some embodiments, the domain DAM function will determinethe location and requirements for the local DAM functions, and thenrequest SONAC entities 361, 381 to instantiate the local DAM functionsin accordance with the requested location and requirements. In oneembodiment, a local DAM function can be co-located with a v-s/u-SGW, iflocal DAMs are established on a per user/service basis. The L-DAMfunctions reply 630 to their respective domain DAM function with theresults. The reply may be in the form of database creation/update withthe requested data. Each domain DAM function then collects data fromeach of its local DAM functions, consolidates 640 this data and mayperform further analysis before replying to the global DAM function.Global DAM 310 then collects data from each of the domain DAM functions,consolidates this data and may perform further analysis if needed beforereplying 650 to the CSM-QoE module. This reply may be in the form of amessage, or by providing a database which includes and organizes therequested data. It should be appreciated that this is just an example,and this procedure can apply for other global requesters, for example aglobal CSM-charging entity.

Further, it should be appreciated that both CSM-QoE assurance andcharging functions can be performed on a per domain level using a domainCSM requester. A procedure for DAM interaction with a CSM requester willnow be discussed with reference to FIGS. 3 and 7, according to anembodiment. FIG. 7 is a flowchart illustrating DAM interaction with adomain CSM entity according to an embodiment. In this example, therequester 325 is a domain CSM entity, for example a CSM-context modulewhich performs service context management. The domain CSM-context modulesends a request 710 to the D-DAM 320, for example for per-servicecontext statistics. In response to the request, the D-DAM 320 configures720 the L-DAMs 330, 332. It should be appreciated that, if necessary,the L-DAMs would need to be instantiated first. Accordingly, if any ofthe local DAMs are not already instantiated, the domain DAM will causethem to be instantiated. In some embodiments, the domain DAM willdetermine the location and requirements for the local DAMs, and thenrequest to a SONAC entity to instantiate the local DAMs in accordancewith the requested location and requirements. The placement of a localDAM function can be context dependent. In one embodiment, a local DAMfunction can be co-located with a v-s/u-SGW, if local DAMs areestablished on a per user/service basis, depending on the applicationpreference and QoS/QoE requirements and functions. If the context is formobile user equipment, and the network utilizes virtual-userconnectivity management (v-u-CM) instances, then the L-DAM function canbe co-located with the v-u-CM. For an example of v-u-CM, see provisionalapplications U.S. Ser. No. 62/186,168 filed Jun. 29, 2015 and U.S. Ser.No. 62/213,452 filed Sep. 2, 2015, both of which are hereby incorporatedby reference in their entirety.

The L-DAMs reply 730 with the results, which can be via signaling, orthe reply may be in the form of database creation/update with therequested data. The D-DAM 320 then collects and consolidates 740 theresults from multiple L-DAMs, and can perform further analysis. Forexample, for a vertical service in which an enterprise customer utilizesa large number of devices and requires further analytics for controllingtraffic between its devices and servers. The D-DAM 320 then replies 750to the requester 325 (in this example, the CSM module). The reply can bein the form of a message and/or in the form of a databasecreation/update with the requested data. It should be appreciated thatthis example can be extended for a global CSM-context module acting asrequester 315 of the global DAM 310.

A procedure for DAM interaction with a VNO requester will now bediscussed with reference to FIG. 8 according to an embodiment. In thisexample, the requester is a VNO, which sends request 810 for VN resourceutilization statistics and VN traffic statistics to the Global DAMfunction. As an example, it is noted this could be useful fordetermining whether a VN or slice update would be useful, for exampleincreasing or reducing the amount of resources allocated to a VN or aslice. Global DAM forwards the request 815 to domain DAMs which areinvolved in the VN. The domain DAMs configure 820 the local DAMs. Itshould be appreciated that the local DAMs should be instantiated priorto configuration. Accordingly, if any of the local DAMs are not alreadyinstantiated, the domain DAM will cause them to be instantiated. In someembodiments, the domain DAM will determine the location and requirementsfor the local DAMs, and then request to a SONAC entity to instantiatethe local DAMs in accordance with the requested location andrequirements based on the logical topology of the VN. In one embodiment,a local DAM can be co-located with a v-s/u-SGW, if local DAMs areestablished on a per user/service basis within the VN. The L-DAMs reply830 to their respective domain DAM with the results. The reply may be inthe form of database creation/update with the requested data. Eachdomain DAM then collects data from each of its local DAMs, consolidates840 this data and may perform further analysis before replying 850 tothe global DAM. Global DAM then collects data from each of the domainDAMs, consolidates 860 this data and may perform further analysis ifneeded before replying 870 to the VNO requester. The replies may be inthe form of a message, or by providing a database which includes andorganizes the requested data. As stated, this information can be used bythe VNO for determining if a VN slice update is desired, which caninclude increasing or reducing the VN resources allocated to the slice.Further, it should be appreciated that VNO resource and trafficutilization statistics can be requested just at the domain level using adomain VNO requester.

As indicated, different entities in the hierarchy can communicate withentities in other levels by providing updates to databases with theupdated data. In some embodiments, this database content can includeGWNI related data regarding the topology of the network, includingcommunication between elements associated with particular clouds andbandwidth capacity; and infrastructure utilization, capacity and loads.The database content can include information related to per slice or perVN resource utilization and loading, as well as per slice or per serviceQoE data.

Embodiments can accommodate networks built to provide a plurality ofservices to a plurality of device types. For example, smart phones orother user equipment may require different types of services (voicecalls, texting, and data file exchanges). Further networks need toconsider the mobility and unpredictable nature of the demands made bysuch devices. Machine to machine customers, for example a utilitycompany deploying thousands of smart meters, may require morepredictable service, possibly with predictable timing and duration.

FIG. 9 is an exemplary block diagram of a processing system 1001 thatmay be used for deploying or instantiating components of the wirelesscommunication network, such as the DAM, CSM and InfM entities. As shownin FIG. 9, processing system 1001 includes a processor 1010, memory1020, non-transitory mass storage 1030, network interface 1050, I/Ointerface 1040, and transceiver 1060, all of which are communicativelycoupled via bi-directional bus 1070. The processing system 1001 furtherincludes input terminals and output terminals, for receiving inputs andoutputs, respectively, from other network components (not shown).

Through the descriptions of the preceding embodiments, the presentinvention may be implemented by using hardware only or by using softwareand a necessary universal hardware platform. Based on suchunderstandings, the technical solution of the present invention may beembodied in the form of a software product. The software product may bestored in a non-volatile or non-transitory storage medium, which can bea compact disk read-only memory (CD-ROM), USB flash disk, or a removablehard disk. The software product includes a number of instructions thatenable a computer device (personal computer, server, or network device)to execute the methods provided in the embodiments of the presentinvention. For example, such an execution may correspond to a simulationof the logical operations as described herein. The software product mayadditionally or alternatively include a number of instructions thatenable a computer device to execute operations for configuring orprogramming a digital logic apparatus in accordance with embodiments ofthe present invention.

Although the present invention has been described with reference tospecific features and embodiments thereof, it is evident that variousmodifications and combinations can be made thereto without departingfrom the invention. The specifications and drawings are, accordingly, tobe regarded simply as an illustration of the invention as defined by theappended claims, and are contemplated to cover any and allmodifications, variations, combinations or equivalents that fall withinthe scope of the present invention.

The invention claimed is:
 1. A method of providing data analyticsinformation, the method executed by a network domain function comprisedin a data analytics management (DAM) system, the method comprising:receiving a request, from a requester, for data analytics information,the request including a request for network slice utilization for avirtual network slice, the virtual network slice comprising a singlevirtual infrastructure that spans multiple physical networks andprovides scalable network resources dedicated and chargeable to aparticular customer entity to provide a service, wherein the requesteris a customer of the DAM system and the requester manages the scalablenetwork resources to meet requirements of the service; configuring aplurality of DAM network functions to collect network data; receivingthe network data from the plurality of DAM network functions; processingthe network data to produce the requested data analytics information tosatisfy the request; and supplying the requested data analyticsinformation to the requester; wherein: the plurality of DAM networkfunctions comprises a global DAM function, a domain DAM function belowthe global DAM function, and a local DAM function below the domain DAMfunction; and configuring the plurality of DAM network functionscomprises the domain DAM function configuring the local DAM function tocollect network data regarding usage from local network infrastructureelements utilized by the virtual network slice.
 2. The method of claim 1wherein configuring the plurality of DAM network functions furthercomprises instantiating any DAM network functions which have not beenpreviously instantiated and are needed to satisfy the request.
 3. Themethod of claim 1 wherein receiving the network data includes retrievingthe network data from a database populated by each of the plurality ofDAM network functions.
 4. The method of claim 1 wherein the local DAMfunctions are instantiated close to the local network infrastructureelements.
 5. The method of claim 1 wherein the local DAM functions areinstantiated within a node for collecting data from a cluster of networkinfrastructure elements.
 6. The method of claim 1 wherein the locationof the local DAM functions are dependent on the nature of the request.7. The method of claim 1 wherein the local DAM functions supplydifferent types of data, with the data being supplied being dependent onthe request.
 8. The method of claim 1 wherein the requester is aninfrastructure manager function.
 9. The method of claim 1 wherein therequester is a Customer Service Management (CSM) function.
 10. A dataanalytics management (DAM) network function comprising: a networkinterface for receiving a data analytics request and for transmittinginstructions; a processor; a non-transient memory for storinginstructions which when executed by the processor cause the dataanalytics management network function to: receive a request, from arequester, for data analytics information, the request including arequest for network slice utilization for a virtual network slice, thevirtual network slice comprising a single virtual infrastructure thatspans multiple physical networks and provides scalable network resourcesdedicated and chargeable to a particular customer entity to provide aservice, wherein the requester is a customer of the DAM system and therequester manages the scalable network resources to meet requirements ofthe service; configure a plurality of additional DAM network functionsto collect network data dependent on the request; process network datareceived from the plurality of additional DAM network functions toproduce the requested data analytics information to satisfy the request;supply the requested data analytics information to the requester;wherein the DAM function is a global function and the plurality ofadditional DAM network functions comprises a domain DAM function belowthe global function and a local DAM function below the domain DAMfunction, the instructions to configure a plurality of additional DAMnetwork functions comprising the domain DAM function configuring thelocal DAM function to collect network data regarding usage frominfrastructure elements utilized by the virtual network slice.
 11. TheDAM network function of claim 10 wherein the instructions to configurethe plurality of additional DAM network functions further compriseinstructions to instantiate any additional DAM network functions whichhave not been previously instantiated and are needed to satisfy therequest.
 12. The DAM function of claim 10 wherein the DAM function is anetwork domain function and each of the plurality of additional DAMnetwork functions are local DAM functions instantiated to collect datafrom local network infrastructure elements.
 13. The DAM function ofclaim 12 wherein the local DAM functions are instantiated close to thelocal network infrastructure elements.
 14. The DAM function of claim 12wherein the local DAM functions supply different types of data, with thetypes of data being supplied being dependent on the request.
 15. Acommunication system comprising a data analytics management (DAM)network function, a requester being a customer of the DAM system and therequester manages the scalable network resources to meet requirements ofa service, and a plurality of DAM network functions, the data analyticsmanagement network function configured to: receive a request, from therequester, for data analytics information, the request including arequest for network slice utilization for a virtual network slice, thevirtual network slice comprising a single virtual infrastructure thatspans multiple physical networks and provides scalable network resourcesdedicated and chargeable to a particular customer entity to provide theservice; configure the plurality of DAM network functions to collectnetwork data; receive the network data from the plurality of DAM networkfunctions; process the network data to produce the requested dataanalytics information to satisfy the request; and supply the requesteddata analytics information to the requester; wherein: the plurality ofDAM network functions comprises a global DAM function, a domain DAMfunction below the global DAM function, and a local DAM function belowthe domain DAM function; and configuring the plurality of DAM networkfunctions comprises the domain DAM function configuring the local DAMfunction to collect network data regarding usage from local networkinfrastructure elements utilized by the virtual network slice.
 16. Thecommunication system of claim 15 wherein the data analytics managementnetwork function is further configured to instantiate any DAM networkfunctions which have not been previously instantiated and are needed tosatisfy the request.
 17. The method of claim 1 further comprisingadjusting an amount of the infrastructure elements utilized by thevirtual network slice based on the data analytics information.
 18. Thedata analytics management (DAM) network function of claim 10 wherein, inresponse to supplying the requested data analytics information to therequester, an amount of the virtual infrastructure utilized by thevirtual network slice is adjusted based on the requested data analyticsinformation.
 19. The communication system of claim 15 wherein, inresponse to supplying the requested data analytics information to therequester, an amount of the virtual infrastructure utilized by thevirtual network slice is adjusted based on the requested data analyticsinformation.
 20. The method of claim 1 wherein the configuring aplurality of DAM network functions comprises configuring the pluralityof DAM network functions based upon physical clusters of infrastructureelements.
 21. The data analytics management (DAM) network function ofclaim 10 wherein the configuring the plurality of additional DAM networkfunctions comprises configuring the plurality of additional DAM networkfunctions based upon physical clusters of infrastructure elements. 22.The communication system of claim 15 wherein the configuring theplurality of DAM network functions comprises configuring the pluralityhierarchy of DAM network functions based upon physical clusters ofinfrastructure elements.
 23. The method of claim 1 wherein the pluralityof DAM network functions further comprises a service specific DAMfunction or a user specific DAM function instantiated below the localDAM function.
 24. The data analytics management (DAM) network functionof claim 10 wherein the plurality of additional DAM network functionsfurther comprises a service specific DAM function or a user specific DAMfunction instantiated below the local DAM function.
 25. Thecommunication system of claim 15 wherein the plurality of DAM networkfunctions further comprises a service specific DAM function or a userspecific DAM function instantiated below the local DAM function.
 26. TheDAM network function of claim 10 wherein the multiple physical networksincludes General Wireless Network Infrastructure (GWNI) elements, thenetwork data including data based on traffic that does not leave theGWNI element, at least one the GWNI elements being a Radio AccessNetwork (RAN) node.
 27. The DAM network function of claim 26 wherein theplurality of DAM entities interfaces with the GWNI element and the dataanalytics information includes an aggregation of data provided by theplurality of DAM network functions.
 28. The communication system ofclaim 15 wherein the multiple physical networks includes GeneralWireless Network Infrastructure (GWNI) elements, the network dataincluding data based on traffic that does not leave the GWNI element, atleast one the GWNI elements being a Radio Access Network (RAN) node. 29.The communication system of claim 28 wherein the plurality of DAMentities interfaces with the GWNI element and the data analyticsinformation includes an aggregation of data provided by the plurality ofDAM network functions.